Measure of analysis performed in property checking

ABSTRACT

The amount of analysis performed in determining the validity of a property of a digital circuit is measured concurrent with performance of the analysis, and provided as an output when a true/false answer cannot be provided e.g. when stopped due to resource constraints. In some embodiments, a measure of value N indicates that a given property that is being checked will not be violated within a distance N from an initial state from which the analysis started. Therefore, in such embodiments, a measure of value N indicates that the analysis has implicitly or explicitly covered every possible excursion of length N from the initial state, and formally proved that no counter-example is possible within this length N.

CROSS-REFERENCE TO PRIORITY APPLICATION

This application is a continuation of U.S. patent application Ser. No. 10/174,379 filed Jun. 17, 2002 which is incorporated by reference herein in its entirety.

BACKGROUND OF THE INVENTION

Exhaustively checking one or more properties in each and every possible state (e.g. of size 1000 bits) and each and every possible input combination to each state by simulation, (e.g. using test vectors) is prohibitively expensive. For this reason, digital circuits (portions thereof or in their entirety) are often analyzed by formal verification, to determine the validity of one or more properties that describe correct and incorrect behaviors in the circuit.

Formal verification of properties can use any of a variety of methods to prove that it is impossible to violate a given property, starting from an initial state or set of initial states of the digital circuit. Tools for formal verification of properties that are available in the prior art (either commercially or from public sources such as universities and laboratories) may be based on any of a number of techniques, such as (1) symbolic model checking, (2) symbolic simulation, (3) explicit state enumeration, and (4) satisfiability (SAT). For background on each of the just-described techniques, see, for example, the following references, each of which is incorporated by reference herein in its entirety:

-   (1) an article by J. R. Burch, E. M. Clarke, K. L. McMillan, D. L.     Dill, and J. Hwang, entitled “Symbolic model checking: 10²⁰ states     and beyond”, published in Information and Computation, Vol. 98, no.     2, June 1992; another article entitled “Coverage Estimation for     Symbolic Model Checking” by Yatin Hoskote, Timothy Kam, Pei-Hsin Ho,     and Xudong Zhao, published in Proceedings of DAC 1999 (Best Paper     Award), pp. 300-305, and a PhD thesis by K. L. McMillan entitled     “Symbolic model checking—an approach to the state explosion     problem”, Carnegie Mellon University, 1992; -   (2) article entitled “Automatic Verification of Pipelined     Microprocessor Control,” by Jerry R. Burch and David L. Dill,     published in the proceedings of International Conference on     Computer-Aided Verification, LNCS 818, Springer-Verlag, June 1994; -   (3) article by E. M. Clarke, E. A. Emerson and A. P. Sistla entitled     “Automatic verification of finite-state concurrent systems using     temporal logic specifications” published in ACM Transactions on     Programming Languages and Systems, 8(2):244-263, 1986; and article     entitled “Protocol Verification as a Hardware Design Aid” by David     Dill, Andreas Drexler, Alan Hu and C. Han Yang published in     Proceedings of the International Conference on Computer Design,     October 1992. -   (4) article entitled “Bounded Model Checking Using Satisfiability     Solving” by Edmund Clarke, Armin Biere, Richard Raimi, and Yunshan     Zhu, published in Formal Methods in System Design, volume 19 issue     1, July 2001, by Kiuwer Academic Publishers.

In addition, see U.S. Pat. No. 5,465,216 granted to Rotem, et al. on Nov. 7, 1995, and entitled “Automatic Design Verification” (that is incorporated by reference herein in its entirety) for an additional example of formal verification tool. See also U.S. Pat. No. 6,192,505 granted to Beer, et al. on Feb. 20, 2001, and entitled “Method and system for reducing state space variables prior to symbolic model checking” that is incorporated by reference herein in its entirety.

Formal verification tools available in the prior art for property checking include, for example, Symbolic Model Verification (SMV) software package available from Carnegie-Mellon University, the coordinated specification analysis (COSPAN) software package available from Bell Laboratories (e.g. at ftp.research.att.com), and the VIS package available from University of California, Berkeley.

For additional information on formal verification tools, see C. Kern and M. R. Greenstreet, “Formal Verification in Hardware Design: A Survey,” in ACM Trans. on Design Automation of Electronic Systems, vol. 4, pp. 123-193, April 1999 that is incorporated by reference herein in its entirety.

Such formal verification tools normally operate on a description of the digital circuit (also called “circuit-under-verification”), which is generated from a hardware description language (HDL) such as Verilog (see “The Verilog Hardware Description Language,” Third Edition, Don E. Thomas and Philip R. Moorby, Kluwer Academic Publishers, 1996) or VHDL (see “A Guide to VHDL”, Stanley Mazor and Patricia Langstraat, Kluwer Academic Publishers, 1992).

Therefore, during prior art testing of a digital circuit, properties or assertions about the correct and incorrect behaviors of the circuit may be checked using a formal verification tool. The properties are normally described using a HDL language such as Verilog or using a property specification language such as Sugar (e.g. available from IBM Research Labs, Haifa, Israel). To validate the correctness of a digital circuit, the formal verification tool must check many properties. The properties may be checked individually sequentially or combined simultaneously. The formal verification tool may start from a single initial state or from a set of initial states for each property.

One method for formal verification of properties is based on so-called bounded model checking (BMC). Such a method may use a Boolean formula that is TRUE if and only if the underlying state transition system can realize a sequence of state transitions that reaches certain states of interest within a fixed number of transitions. If such a sequence cannot be found at a given length, k, the search is continued for larger k. The procedure is symbolic, i.e., symbolic Boolean variables are utilized; thus, when a check is done for a specific sequence of length k, all sequences of length k from an initial plate are examined. A Boolean formula that is formed for each sequence is used by the tool, and if a satisfying assignment is found, that assignment is a “witness” (also called “counter example”) for the sequence of interest.

Such a formal verification tool has three possible results for each Boolean formula: the formula is proven true; a counter-example is produced; or the tool cannot determine the truth of the Boolean formula because memory or compute resource limits prevent completion of the checking. The last-described result (i.e. “cannot determine”) is often the case when such a tool is applied to a real-world digital circuit (such as a microprocessor) that has a large number of transistors (in the order of 1-5 million), because of the well known “state explosion problem”

As described in “Architecture Validation for Processors”, by Richard C. Ho, C. Han Yang, Mark A. Horowitz and David L. Dill, Proceedings 22.nd Annual International Symposium on Computer Architecture, pp. 404-413, June 1995, “modern high-performance microprocessors are extremely complex machines which require substantial validation effort to ensure functional correctness prior to tapeout” (see page 404). As further described in “Validation Coverage Analysis for Complex Digital Designs” by Richard C. Ho and Mark A. Horowitz, Proceedings 1996 IEEE/ACM International Conference on Computer-Aided Design, pp. 146-151, November 1996, “the functional validation of state-of-the-art digital design is usually performed by simulation of a register-transfer-level model” (see page 146).

A number of metrics for verification tools are described in the prior art, for example, see the following articles:

-   (1) Hoskote, Y. V., et al., “Automatic Extraction of the Control     Flow Machine and Application to Evaluating Coverage of Verification     Vectors”, International Conference on Computer Design: VLSI in     Computers & Processors, Oct. 2-4, 1995, pp. 532-537; -   (2) Moundanos, D., “Abstraction Techniques for Validation Coverage     Analysis and Test Generation”, IEEE Transactions on Computers, vol.     47, January 1998, pp. 2-14; -   (3) Devadas, S., et al., “An Observability-Based Code Coverage     Metric for Functional Simulation”, IEEE/ACM International Conference     on Computer-Aided Design, Nov. 10-14, 1996, pp. 418-425; and -   (4) Geist, D., et al., “Coverage-Directed Test Generation Using     Symbolic Techniques”, Formal Methods in Computer-Aided Design, First     International Conference, FMCAD 96, Palo Alto, Calif., Nov. 6-8,     1996, pp. 142-159.     Each of the above-referenced articles (1)-(4) is incorporated by     reference herein in its entirety.

See U.S. Pat. No. 6,102,959 granted to Hardin, et al. on Aug. 15, 2000 and entitled “Verification tool computation reduction” that is incorporated by reference herein in its entirety.

U.S. Pat. No. 6,311,293 granted to Kurshan, et al. on Oct. 30, 2001 and entitled “Detecting of model errors through simplification of model via state reachability analysis” that is incorporated by reference herein in its entirety.

Also incorporated by reference herein in their entirety are the following: U.S. Pat. No. 6,356,858 granted to Malka, et al. on Mar. 12, 2002 and entitled “Coverage measurement tool for user defined coverage models”; U.S. Pat. No. 5,724,504 granted to Aharon, et al. on Mar. 3, 1998 and entitled “Method for measuring architectural test coverage for design verification and building conformal test”.

Also incorporated by reference herein in their entirety are the following references:

-   “Algorithms for the Satisfiability (SAT) problem: A Survey” by Jun     Gu, Paul W. Purdom, John Franco, and Benjamin W. Wah, DIMACS Series     on Discrete Mathematics and Theoretical Computer Science 35:19-151,     American Mathematical Society, 1997; -   “A machine program for therorem-proving” by Martin Davis, George     Longemann, and Donald Loveland in Communications of the ACM,     5(7):394-497, July 1962; and -   “Chaff: Engineering an Efficient SAT Solver” by M. W.     Moskewicz, C. F. Madigan, Y. Zhao, L. Zhang, and S. Malik, in 38th     Design Automation Conference (DAC '01), June 2001, pp. 530-535.

SUMMARY

A computer is programmed in accordance with the invention, to use a formal verification tool to check for a counter-example of a property in a high level description (HLD) of a digital circuit, and concurrent with use of the tool, to maintain a measure of the analysis being performed by the tool. In certain embodiments, a measure of analysis performed without finding a counter-example, is reported to the user when the tool stops due to a limit on one or more resources, and without producing a proof or finding a counter-example.

Such an analysis measure may be used as a guide for future testing, or to terminate testing. In some embodiments, a value N for the analysis measure indicates that a given property will not be violated within N sequential transitions through a number of states reachable from a user-specified initial state. Therefore, in such embodiments, the measure (also called “proof radius”) of value N indicates that the formal verification tool has exhaustively covered every possible excursion of length N from the initial state, and formally proved that no error is possible.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates, in a flow chart, one embodiment of a method for use of a formal verification tool to check a property, while maintaining a measure of the work done.

FIGS. 2A and 2C each illustrate, in a diagram of state space, the states visited by a formal verification tool in performing one and two iterations respectively, of the method of FIG. 1.

FIGS. 2B and 2D each illustrate, a logic cone representative of the property being checked when the states of FIGS. 2A and 2C respectively are visited, and a storage element indicative of the amount of work done by the formal verification tool.

FIG. 2E illustrates, a logic cone representative of a counter-example to the property being found in a fifth iteration of the method of FIG. 1.

FIG. 3 illustrates, in a flow chart, one specific implementation of the method of FIG. 1.

FIG. 4 illustrates, in a conceptual diagram, use of formal verification with simulation to find defects in the description of a circuit.

DETAILED DESCRIPTION

In accordance with the invention, a formal verification tool is used to iteratively check that a property (such as a Boolean formula) is satisfied by all states that are within a certain number of transitions (e.g. 1 transition) starting from an initial state (which may be, for example, specified by the user). For example, as illustrated in FIG. 1, a method 100 uses the tool in act 101 to perform one iteration, and checks if a resource limit has been reached in act 103 and if not, returns to act 101 via branch 105.

In several embodiments, at each iteration of the method, a measure (also called “proof radius”) is maintained, of the analysis being performed by the tool in act 101 without finding a counter-example to the property being checked e.g. in an act 102 as shown in FIG. 1. In some embodiments of the invention, the formal verification tool is used to conduct a breadth-first search of the state space, wherein the number “n” of transitions from a current state is set to one. In other embodiment the search need not be breadth first, e.g. if the tool checks the property for n (greater than one) successive transitions from the current state. Regardless of the type of search, the depth reached by the tool (in number of sequential transitions through number of reachable states) from the initial state without finding a counter example is maintained in act 102, as a measure of the analysis that has been done. When a limit on one or more resources is reached (as determined in act 103), method 100 stops iteration and instead goes to act 104. In act 104, the method reports the measure as an indication of the amount of analysis that has been done without finding a counterexample to the property being checked.

The analysis measure being reported by method 100 (e.g. in act 104) is indicative of the amount of analysis that has been performed (e.g. the depth to which the search progressed) during formal verification, without finding a counter-example for the property being checked. Such a measure may be used as a guide for future testing, or to terminate testing, depending on the embodiment.

Operation of method 100 (FIG. 1) is now described in the context of an example illustrated in FIG. 2A. In this example, a state space 200 contains a number of states 201-207 that are representative of a digital circuit (based on its description in HDL). Assume that method 100 starts from an initial state 201. Initial state 201 may be selected by a user. Alternatively initial state 201 may be obtained from testbenches used in simulation (e.g. in a commercially available simulator such as VCS from Synopsys, Mountain View, Calif.).

When starting from states in a simulation testbench, method 100 uses a formal verification tool to explore orders of magnitude more of a digital circuit's state-space than traditional black-box simulation testbenches. Specifically, a formal verification tool (when used as described herein) performs analysis equivalent to simulating every possible legal sequence of inputs in the simulation cycles surrounding the test vector stimuli. By doing this, method 100 significantly increases the state coverage of the digital circuit and highlights many corner-case issues missed by simulation alone. In this manner, method 100 amplifies the user-specified simulation test stimuli, as illustrated in FIG. 4.

Referring to FIG. 4, a description of the design, 401, written in a hardware description language (e.g. Verilog) contains properties or checkers, 404, and constraints, 405. A simulation vector, 403, traverses a particular sequence of states of the design. Method 100 amplifies said simulation vector to analyze a larger set of states of the design, 402, searching for input sequences which will cause a property to be violated. Because this formal analysis is based on user-specified constraints, only legal input sequences are considered, which minimizes the number of fake findings of counter examples (also called “false firings”).

Referring to the example in FIG. 2A, in performing act 101, a property that has been specified by the user is exhaustively checked (either explicitly or implicitly) in states 202 and 203 that can be reached from state 201 within a preset number n of sequential transitions (e.g. one transition) through zero or more states in the current act 101. If no counter example is found for the property, then an analysis measure 209 (FIG. 2B) is incremented (as per act 102) before returning to act 101 (via branch 105).

In one implementation, the property is not checked by simulation of each state that is one transition (i.e. n=1) away from initial state 201. Instead, a fan-in cone of logic 210 (FIG. 2B) is used to determine which inputs 218 and 219 are needed to generate an output condition that is known to be a counter-example for the property. The just-described fan-in cone of logic 210 may be determined by a transitive fanin. A transitive fanin is all the primary inputs and intermediate variables 214, 215, and 216 used by a state variable 211, wherein the state variable represents a logic element or a storage element in a circuit description.

The just-described counter-example may be determined from the property itself (by negating a Boolean expression for the property). The formal verification tool of some embodiment builds up a set of logic equations (in act 101 in FIG. 1) that represent the performance of a preset number of simulation cycles through a logic tree representative of the digital circuit being tested. By solving these equations, the tool determines whether a counter-example for a given property is reachable from states that are currently being visited (e.g. states 201-203). If a counter-example is not found, a storage element 209 (FIG. 2B) is incremented (e.g. from 0 to 1).

Therefore, in this specific implementation, the tool evaluates only states located within a register-transfer-level (RTL) logic cone 210 (FIG. 2B) that is associated with checking a property. In this manner, the tool does not verify states in the whole digital circuit description (e.g. represented by states 211-214 within the cone), thereby to simplify the task of checking the property.

Note however, that any other property checking tool can be used to perform act 101 in method 100 (FIG. 1). The just-described proof radius may be computed for a symbolic simulation tool or an explicit state enumeration tool although some embodiments (discussed herein) maintain and provide the proof radius for a tool that uses bounded model checking (BMC) to look for errors in the description of a digital circuit.

In a second iteration of method 100 in this example, act 101 is repeated, now by visiting states 204-207 (FIG. 2C) that are two sequential transitions away from state 201 and that are reachable from the states 202 and 203 (which were located one transition away). Once again, in actual implementation, states in a larger cone 220 (FIG. 2D) are visited, in checking whether a counter-example to the property is reachable. Again, if no counter-example is found reachable, the storage element 209 is incremented (e.g. to value 2) in act 102, and if resource limits are not yet reached, branch 105 is again taken.

In this manner, the method 100 is performed iteratively until a counter-example 260 is reached from a state 251 (which is five sequential transitions away in this example). At this stage, storage element 209 (which had been incremented in repetitively performing act 103) has the value 4. Note that if a resource limit had been reached prior to reaching state 251, then the value 4 is displayed by method 100 (as per act 104). The value 4 for the proof radius indicates that the property being checked will not be violated within 4 sequential transitions from the initial state 201. Therefore, in such embodiments, value 4 indicates that the formal verification tool has exhaustively covered every possible excursion of length 4 from the initial state 201, and formally proved that no error is possible within this distance 4. As used herein the terms “length” and “distance” are intended to mean sequential transitions from an initial state.

In several embodiments, a computer is programmed to perform the following acts: starting at an initial state, set to zero a variable (also called “proof radius”) that is indicative of the amount of analysis done so far (see act 301 in FIG. 3), set to one transition the range of analysis for the formal verification tool (see act 302), analyze one transition of behavior of the digital circuit to determine validity of a given property (see act 303), check if a counter-example to the property is found (see act 304) and if not found, check if a resource limit is reached (see act 306) and if not increment the proof radius and the range of analysis (see act 307), and return to act 303. When a counter example is found in act 304, report the value in the proof radius as a measure of the work done by the formal verification tool and also report the counter example (in act 305). When a resource limit is reached in act 306, the computer is programmed to report the proof radius (in act 308).

In some embodiments, if a digital circuit contains multiple clocks that operate at different frequencies, for such circuits, the proof radius is maintained in units of the greatest common divisor of all clock periods. For example if the digital circuit contains two docks of periods 15 and 20 nanoseconds, then the greatest common divisor is 5 nanoseconds (which is not any of the original clock periods).

Although the above description refers to only checking of one property, to functionally verify a digital circuit's description (in HDL), many properties may need to be proven. Moreover, the results of a formal tool may be different for each property: e.g. a subset of the properties will be proven, another subset will have counter-examples found and a third subset will have unproven properties with a proof radius reported for each property as a measure of the analysis performed.

Therefore, to obtain better functional verification of a digital circuit description, a formal verification tool can be repetitively applied to all such properties (in act 101 in FIG. 1) before going to act 102, and when returning back via branch 105 then the tool may be applied only to subsets, of all unproven properties. In some embodiments, on returning back via branch 105, method 100 may increase the resource limits each time.

Furthermore, in some embodiments, the proof radius may be used to select a subset of the unproven properties for further analysis as follows: (1) sort list of unproven properties in ascending order of proof radius, (2) select a percentage (p %) of properties for further analysis, (3) select the properties in the top p % of the sorted list, (4) repeat analysis on selected subset of properties with higher resource limits.

As discussed above, in method 100 (FIG. 1), use of a formal verification tool needs to start from an initial state, also known as a seed state. In some embodiments, act 101 (FIG. 1) is repeatedly performed from many seed states. When method 100 is performed for a number of seed states, the proof radius of each property may be reported in three forms: (1) minimum proof radius achieved during analysis from all the seed states, (2) the average proof radius achieved during analysis from all the seed states, and (3) the maximum proof radius achieved during analysis from all the seed states. Depending on the embodiment, the report of proof radius may be given at periodic intervals during execution of the formal algorithm and/or at the end of the analysis.

In a first example, a report of the proof radii achieved for 4 properties starting from several initial states (also called “seeds”) is illustrated below.

Proof Radius Summary by Property Average Min Property Name 4.50 4 fire cs3232_top.c0.u_MAS3232.fire fire 0 3.50 3 fire cs3232_top.c0.u_MAS3232.fire_0 fire 0 4.20 3 fire cs3232_top.c0.u_MAS3232.fire_1 fire 0 10.50 6 fire cs3232_top.c0.u_MAS3232.fire_10 fire 0

In the above example, the proof radius is reported in two statistical forms over multiple states: an average and a minimum (although other statistical forms, such as a median and/or standard deviation and/or maximum may be reported in other examples). The average proof radius is obtained as a mean of the values of the proof radius for each seed, while the minimum proof radius is the smallest value across all seeds.

A large difference between the average and minimum proof radius values (as seen in the last property in the exemplary table above) may be used to increase the memory and/or computation time resources (e.g. for the last property in the table), so that eventually the difference in proof radii is more uniform across all properties. So, the proof radius can be used as a feedback, to identify one or more properties that need more effort (such additional effort is focused on the last property in the above exemplary table, while the remaining properties are not further analyzed).

In a second example, a circuit-under-verification includes a counter that increments when a primary input is asserted. A high level description (HDL) of a circuit-under-verification in the Verilog language is shown in Appendix 1 below. The property to be checked is:

count<=128

In one embodiment of method 100, the formal tool used to check the property is based on the bounded model checking (BMC) technique. Specifically, an initial state (of the circuit described in the above Verilog code) is given by the user to the formal verification tool, and in this initial state the variable “count” has been set to 0. At this time, method 100 sets the analysis measure (proof radius) to 0.

Next, at the first cycle, the BMC technique examines behavior of the counter in the Verilog code, and finding no counter-example (where the variable “in” is asserted for more than 128 total cycles), increments the proof radius to 1. This process continues until a termination condition is reached. The termination condition is one of: (1) a resource limit is reached, for example, a pre-determined computation limit, or (2) a counter-example to the property is found. At each repetition of act 101 (which corresponds to one step of the BMC technique), the proof measure is incremented.

The proof radius can also be used for comparing different formal property checking algorithms. In one embodiment, the number of seed states that can be analyzed to a fixed proof radius for a given set of properties in a given time period is measured, and compared across different algorithms. In another embodiment, the proof radius achieved for a single property in a given time period is measured, and compared.

Illustrative software source code for calculating and displaying proof radius for a number of properties in one specific example is provided in Appendix 2 below.

A computer may be programmed in the manner described herein to perform formal analysis around each state that a user simulates, with each assertion (which may be, for example, specified by the user) as a property to be checked. Moreover, in one embodiment, the user simply sets a variable (also called “effort variable”) to one of three values: low, medium, and high, and the computer is programmed to automatically compute the amount of each resource to be used for each assertion for each state. For example, the computer may equally divide a total amount of compute resource usage metric (e.g. CPU time or memory) by the product (number of assertions×number of states) to arrive at a budget of that resource for each assertion in each state. Instead of compute resource usage metric, another unit, such as the number of gates or the complexity of logic may be used to divide up the limited resources, to arrive at an alternative budget for each assertion for each state.

Some embodiments compare different SAT-based BMC techniques, and in such embodiments the computer resource usage is measured in terms of the number of backtracks, where backtrack refers to a standard backtracking operation performed by prior art SAT solvers (e.g. see the above-referenced articles entitled “Algorithms for the Satisfiability (SAT) problem: A Survey”, “A machine program for therorem-proving” and “Chaff: Engineering an Efficient SAT Solver”).

Although in some embodiments, the computer resources are equally divided after a run is started, the user may decide to allocate more computer resources to a specific subset of states or a specific subset of assertions, e.g. by setting the effort variable to high for a given run, and to low for another run.

Numerous modifications and adaptations of the embodiments, examples, and implementations described herein will be apparent to the skilled artisan in view of the disclosure. For example, in certain embodiments of the type described above, a computer is programmed with a formal verification tool to simultaneously check a number of properties, and also maintain a proof radius for each property. A large difference in values between proof radii of different properties may be used to further test (either automatically or with manual approval) those properties that have a lower proof radius, thereby to obtain greater confidence in the overall design of the circuit.

A metric of the type described herein (e.g. the proof radius) can be used to provide a level of confidence to a user: the larger the value, the more confidence the user may have in the circuit under verification. As N tends to infinity, the user may decide that there is no bug (also called “defect”) in the digital circuit if there is no counter-example. A value of N less than infinity may be used in verifying descriptions of complex real-world digital circuits, to stop testing based on practical experience. In one example, testing may be stopped when a proof radius value becomes larger than the actual or estimated diameter of the digital circuit (wherein the diameter is the minimum distance (or number of sequential transitions from an initial state) required to reach the farthest state among all possible reachable states).

A method to measure the speed of an exhaustive property checking algorithm, includes calculating a first proof radius of a first property on a first seed using a fixed budget of time, and comparing with a corresponding proof radius for another algorithm. Another method to measure the speed of an exhaustive property checking algorithm includes calculating the computation time used by said property checking algorithm to reach a pre-determined proof radius, and comparing with a corresponding computation time for another algorithm.

Moreover, a method to compare the performances of a plurality of property checking algorithms in some embodiments includes calculating the proof radius of a first property achieved by a first property checking algorithm on a first seed state, calculating the proof radius of said property achieved by a second property checking algorithm on said seed state, and comparing the first and second proof radii.

In the just described method, in some embodiments, the minimum, maximum and average proof radii of said property for a plurality of seed states are compared for different algorithms. Also in the just-described method, in several embodiments, the minimum, maximum and average proof radii of a plurality of properties are compared for said seed state. Furthermore, in some embodiments of the just-described method, the minimum, maximum and average proof radii of a property are compared for a plurality of seed states.

A metric of the type described herein can be used to benchmark different formal verification tools, e.g. by providing the same problem to multiple tools and comparing the resulting proof radii (i.e. same digital circuit, same properties and same budget yield different proof radii for the different tools due to difference in techniques being used by the two tools).

Another way to benchmark different formal verification tools is by stopping the tools when a certain proof radius is reached, when working on the same problem, and comparing the resources used by the two tools (e.g. to determine which tool finished first). One variant of this method is to determine the number of initial states that can be processed by each tool, e.g. within one second of computation time (i.e. states/second).

Numerous such modifications and adaptations of the embodiments described herein are encompassed by the attached claims.

APPENDIX 1 module DUV(clock, areset, in); input clock; input reset; input in; reg [31:0] count; always @(posedge clock or posedge areset) begin  if (areset == 1′b1) begin   count <= ′b0;  else  if (in == 1′b1) begin   count <= count + 1;  end end endmodule

APPENDIX 2 /* Structure definitions */ typedef struct StatsS {  /* chx based stats */  int *nAborts;   /* count of seeds first abort at unroll i */  int nNoAborts;    /* count of seeds no aborts up to max unroll */  boolean firingLimitReached;  /* scratch values */  int clockPeriod;  boolean atMaxUnroll;  int *isAborted;   /* unroll of earliest abort (0 if no aborts) for            seed i cycles from cur horizon */ } SStats, *Stats; typedef struct ctxt_struct {  /* Context stuff */  int min_unroll;  int max_unroll;  int chkr_budget;    /* checker budget */  int n_trgtChxs;  int n_firedTrgtChxs;  int n_trgts;  TrgtStatusS *trgts_status;  ChxStatsS *trgtChxs_stats;  int min_budget;  int max_budget; } ctxt_struct, *ctxt; /* Code to display (and compute) proof radius */ void display_proof_radius_summary (  ctxt scc) /* context with global data about algorithm */ {  int i;  bool isFound;  chx_defn chx;  const char *chxName;  double aveProofRadius;  int nTargets = 0;  double sumOfAverages = 0;  /* print proof radius summary */  printf(“\n”);  printf(“-------------------------------------------------------------------------------\n”);  printf(“Proof Radius Summary by Target\n”);  printf(“-------------------------------------------------------------------------------\n”);  printf(“%10s %10s %s\n”, “Average”, “Minimum”, “Check Name”);  printf(“-------------------------------------------------------------------------------\n”);  for_all_properties(properties, i, chx) { /* For each property */   Stats stats; /* Structure containing stats from formal analysis (BMC)*/   get(chx, &stats); /* Get the stats structure for 1 property */   if (!check_fired(chx)) {    int minProofRadius = scc->max_unroll;    int sigmaProofRadii = 0;    int nSeeds = 0;    int ur;    /* aborts have proof radius of (unroll - clockPeriod)... */     for (ur = scc->max_unroll; ur > scc->min_unroll; −−ur) {      if (stats->nAborts[ur]) {       int proofRadius = ur − stats->clockPeriod;       nSeeds += stats->nAborts[ur];       sigmaProofRadii += proofRadius * stats->nAborts[ur];       minProofRadius = proofRadius;      }    }    /* ...except at min_unroll where the proof radius is zero */    if (stats->nAborts[scc->min_unroll]) {      nSeeds += stats->nAborts[scc->min_unroll];      minProofRadius = 0;    }    /* seeds with no aborts have proof radius of max unroll */    nSeeds += stats->nNoAborts;    sigmaProofRadii += scc->max_unroll * stats->nNoAborts;    /* check if there is a seed not yet counted */    if (stats->atMaxUnroll && !stats->isAborted[scc->max_unroll]) {      ++nSeeds;      sigmaProofRadii += scc->max_unroll;    }    chxName = get_name(chx);    aveProofRadius =      (nSeeds) ? DIV(sigmaProofRadii, nSeeds) : minProofRadius;    printf(“%10.2f %10d %s\n”,             aveProofRadius,             minProofRadius,             chxName);    sumOfAverages += aveProofRadius;    nTargets++;   }  } end_for; } /* Code to find search for counter-examples to properties and  keep track of information for proof radius calculation */ static void search_targets (  ctxt   scc,  int unrollLimit,  state_id *Sids) {  int unroll, i;  /* update stats */  for (i=0; i<scc->n_trgtChxs; ++i) {   Stats cs = &scc->trgtChxs_stats[i];   if (cs->atMaxUnroll && !cs->isAborted[scc->max_unroll]) {    ++cs->nNoAborts;   }   for (unroll = scc->max_unroll−1; unroll >= scc->min_unroll; −−unroll) {    cs->isAborted[unroll+1] = cs->isAborted[unroll];   }   cs->isAborted[scc->min_unroll] = 0;   cs->atMaxUnroll = FALSE;  }  /* search for firings */  for (unroll = unrollLimit, unroll >= scc->min_unroll; −−unroll) {   unsigned phase;   state_id Sid = Sids[unroll];   /* for each target... */   for (i=0; i<scc->n_trgts; ++i) {    TrgtStatusSP ts = &scc->trgts_status[i];    /* is target not max-ed out on firings? */    if (!ts->stats->firingLimitReached) {      /* is the current unroll approprate for target? */      ts->retry[scc->min_unroll] = TRUE;      if (ts->retry[unroll]) {       ts->retry[unroll] = FALSE;       /* is clock phase #not# appropriate for target? */       if (!ts->activePhases[phase] || (unroll % ts->clockPeriod)) {        /* try again at higher unroll! :-) */       ts->retry[unroll+1] = TRUE;        continue;       }       /* does target already fire on the seed? */       if (is_fired_in_state(scc->scdb, ts->trgt, Sid)) {        /* do not bother trying to make it fire again */        continue;       }       /* else */ {        find_firing_result_s result = { 0 };        find_firing_args_s args = { 0 };        int baseCnstrBudget;        int nFirings;        chx_stats chxStats;        /* OK, search for target firing! */        args.unroll = unroll;        args.budget =         MIN(scc->max_budget,              (ts->baseBudget[unroll] +              ts->bonusBudget[unroll]));        baseCnstrBudget = (2 * ts->baseBudget[unroll]) − scc- >min_budget;        args.constraintBudget =         MIN(2 * scc->max_budget,              (baseCnstrBudget +              ts->bonusCnstrBudget[unroll]));        /* Search for counter-example to properties by applying the BMC technique and obtain a result in the “result” structure*/        find_firing(scc->fc, ts->trgt, &args, &result);        /* digest result */        switch (result.status) {        case ABORT:         /* reduce baseline budget if too many aborts */         if (!result.cachedResultUsed) {           ts->nCredits[unroll]−−;           if (ts->nCredits[unroll] == 0) {            /* reduce baseline budget */            int j;            for (j = unroll; j <= scc->max_unroll; ++j) {             ts->nCredits[j] = scc->budgetReductionThreshold;             if (ts->baseBudget[j] > scc->min_budget) {              ts->baseBudget[j] −= 1;             }            }           }         }         /* update proof radius stats */         if (!ts->stats->isAborted[unroll]) {           ts->stats->isAborted[unroll] = unroll;           ++ts->stats->nAborts[unroll];         }         break;        case OK:         /* stop searching target if it fires too often */         chxStats = get_stats(ts->stats->chx);         nFirings = count(chxStats->firings);         break;        case INCONSISTENT:         if (unroll < scc->max_unroll) {           /* try again at higher unroll! :-) */           ts->retry[unroll+1] = TRUE;         } else {           ts->stats->atMaxUnroll = TRUE;         }         break;        default:        }       }      }    }   }  } } 

1-14. (canceled)
 15. A method for using a formal verification tool to verify a property of a circuit, the method comprising, with a computer: analyzing the behavior of the circuit for a number of cycles of operation, wherein the analyzing comprises verifying the property based at least in part on the value of a proof radius variable using the formal verification tool; checking whether a counterexample to the property is found; and iteratively repeating the analyzing and the checking, wherein the iteratively repeating comprises: if a counterexample is not found, then increasing the value of the proof radius variable, and if a counterexample is found, a stopping variable reaches a predetermined limit, or a counterexample is found and a stopping variable reaches a predetermined limit, then stopping the repeating the analyzing and the checking.
 16. The method of claim 15, wherein the stopping variable is based at least in part on the proof radius variable.
 17. The method of claim 15, wherein the stopping variable is based at least in part on usage of a resource.
 18. The method of claim 15, further comprising reporting the value of the proof radius variable after the stopping as a measure of the amount of analysis performed by the formal verification tool.
 19. The method of claim 15, further comprising reporting at least one or more of the following: a minimum proof radius, an average proof radius, a median proof radius, a standard deviation of a proof radius, a difference between a minimum proof radius and a maximum proof radius, or a maximum proof radius.
 20. The method of claim 15, wherein a seed state for starting the analyzing is obtained from a simulation.
 21. The method of claim 15, wherein a seed state for starting the analyzing is at least partially specified by the user.
 22. The method of claim 15, further comprising: repeating one or more sequences of the analyzing, the checking, and the iteratively repeating, wherein the analyzing for each of the repeated sequences is based on behavior of the circuit starting from a respective seed state for starting the analyzing for a corresponding sequence, the repeating producing a proof radius value for each of the sequences; and reporting a measure of analysis based on the proof radius values produced by the repeating, each of the proof radius values corresponding to a respective one of the seed states.
 23. The method of claim 15, further comprising storing at least one or more of the following in a machine-readable medium: the value of the proof radius variable, a minimum proof radius, an average proof radius, a median proof radius, a standard deviation of a proof radius, a difference between a minimum proof radius and a maximum proof radius, or a maximum proof radius.
 24. The method of claim 15, further comprising manufacturing the circuit after using the formal verification tool to verify the property of the circuit.
 25. A method, comprising: analyzing the behavior of a circuit starting from a seed state for a first number of cycles of operation, wherein the analyzing comprises using a processor to verify a property of the circuit based at least in part on the value of a first proof radius variable using a first formal verification tool; analyzing the behavior of the circuit starting from the seed state for a second number of cycles of operation, wherein the analyzing comprises using a processor to verify a property of the circuit based at least in part on the value of a second proof radius variable using a second formal verification tool; and comparing the first proof radius and the second proof radius to determine a relative performance of the first and second formal verification tools.
 26. The method of claim 25, wherein: the analyzing for the first number of cycles comprises verifying the property of the circuit until a first predetermined budget of processing time has elapsed; and the analyzing for the second number of cycles comprises verifying the property of the circuit until a second predetermined budget of processing time has elapsed.
 27. The method of claim 26, wherein the first predetermined budget of processing time, the second predetermined budget of processing time, or the first predetermined budget of processing time and the second predetermined budget of processing time are at least partially specified by the user.
 28. The method of claim 25, wherein the method further comprises: stopping the analyzing for the first number of cycles when the first proof radius reaches a first predetermined proof radius limit to determine a first amount of processing time required to reach the first predetermined proof radius limit; and the analyzing for the second number of cycles when the second proof radius reaches a second predetermined proof radius limit to determine a second amount of processing time required to reach the second predetermined proof radius limit; and comparing the first amount of processing time and the second amount of processing time to determine a relative performance of the first and second analysis tools.
 29. The method of claim 25, wherein: the analyzing for the first number of cycles comprises two or more iterations of the first formal verification tool, wherein: if a counterexample is not found by the first formal verification tool during each of the respective iterations, then increasing the value of the first proof radius variable; and if a counterexample is found by the first formal verification tool during one of the iterations, then stopping the analyzing.
 30. One or more machine-readable storage media storing machine-readable instructions that when executed by a computer cause the computer to perform the method of claim
 25. 31. A method for determining a performance rating of a formal verification tool, the method comprising: determining a proof radius for a property of a circuit using a programmed computer to formally verify the property with the formal verification tool until a predetermined limit is met; determining a performance rating for the analysis tool, wherein the performance rating is based on at least in part on the proof radius.
 32. The method of claim 31, wherein the predetermined limit is based at least in part on a predetermined budget of processing time that elapses during the formally verifying.
 33. The method of claim 31, wherein the predetermined limit is based at least in part on a reaching a proof radius limit during the formally verifying.
 34. The method of claim 31, wherein the predetermined limit is at least partially specified by a user. 